Skip to content

Remove regenerate-maven-poms tool#2326

Merged
DMarby merged 2 commits intomainfrom
dmarby/rm-maven-pom-regen
Mar 16, 2026
Merged

Remove regenerate-maven-poms tool#2326
DMarby merged 2 commits intomainfrom
dmarby/rm-maven-pom-regen

Conversation

@DMarby
Copy link
Member

@DMarby DMarby commented Mar 13, 2026

And the logic to add the stage to the dockerfiles, as all existing plugins that should have maven poms/deps stages have them, and any new versions gets them from the Dockerfile that gets copied from previous versions (and then the fetcher regenerates the .pom).

The fetcher copies old dockerfiles which already have maven-deps
stages. Any new versions inherit those stages, then regenerate.go
handles the pom.xml generation. Remove the unnecessary logic that was
adding stages to dockerfiles and the regenerate-maven-poms CLI tool.
@DMarby DMarby marked this pull request as draft March 13, 2026 19:07
The pom.xml still needs to be regenerated for new plugin versions.
Only the Dockerfile stage insertion was meant to be removed.
@DMarby DMarby marked this pull request as ready for review March 13, 2026 19:12
@DMarby DMarby requested review from pkwarren and stefanvanburen and removed request for stefanvanburen March 13, 2026 19:12
@DMarby DMarby merged commit 265bd61 into main Mar 16, 2026
3 checks passed
@DMarby DMarby deleted the dmarby/rm-maven-pom-regen branch March 16, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants